<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
  <head>
    <title>
Bugzilla::Hook</title>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  <link rel="stylesheet" title="style" type="text/css" href=".././../../../style.css" media="all" >

</head>
  <body id="pod">
<p class="backlinktop"><b><a name="___top" href="../index.html" accesskey="1" title="All Documents">&lt;&lt;</a></b></p>
<h1>Bugzilla::Hook</h1>
<div class='indexgroup'>
<ul   class='indexList indexList1'>
  <li class='indexItem indexItem1'><a href='#NAME'>NAME</a>
  <li class='indexItem indexItem1'><a href='#SYNOPSIS'>SYNOPSIS</a>
  <li class='indexItem indexItem1'><a href='#DESCRIPTION'>DESCRIPTION</a>
  <ul   class='indexList indexList2'>
    <li class='indexItem indexItem2'><a href='#How_Hooks_Work'>How Hooks Work</a>
  </ul>
  <li class='indexItem indexItem1'><a href='#SUBROUTINES'>SUBROUTINES</a>
  <li class='indexItem indexItem1'><a href='#HOOKS'>HOOKS</a>
  <ul   class='indexList indexList2'>
    <li class='indexItem indexItem2'><a href='#attachment_process_data'>attachment_process_data</a>
    <li class='indexItem indexItem2'><a href='#auth_login_methods'>auth_login_methods</a>
    <li class='indexItem indexItem2'><a href='#auth_verify_methods'>auth_verify_methods</a>
    <li class='indexItem indexItem2'><a href='#bug_columns'>bug_columns</a>
    <li class='indexItem indexItem2'><a href='#bug_end_of_create'>bug_end_of_create</a>
    <li class='indexItem indexItem2'><a href='#bug_end_of_create_validators'>bug_end_of_create_validators</a>
    <li class='indexItem indexItem2'><a href='#bug_end_of_update'>bug_end_of_update</a>
    <li class='indexItem indexItem2'><a href='#bug_fields'>bug_fields</a>
    <li class='indexItem indexItem2'><a href='#bug_format_comment'>bug_format_comment</a>
    <li class='indexItem indexItem2'><a href='#buglist_columns'>buglist_columns</a>
    <li class='indexItem indexItem2'><a href='#bugmail_recipients'>bugmail_recipients</a>
    <li class='indexItem indexItem2'><a href='#colchange_columns'>colchange_columns</a>
    <li class='indexItem indexItem2'><a href='#config_add_panels'>config_add_panels</a>
    <li class='indexItem indexItem2'><a href='#config_modify_panels'>config_modify_panels</a>
    <li class='indexItem indexItem2'><a href='#email_in_before_parse'>email_in_before_parse</a>
    <li class='indexItem indexItem2'><a href='#email_in_after_parse'>email_in_after_parse</a>
    <li class='indexItem indexItem2'><a href='#enter_bug_entrydefaultvars'>enter_bug_entrydefaultvars</a>
    <li class='indexItem indexItem2'><a href='#flag_end_of_update'>flag_end_of_update</a>
    <li class='indexItem indexItem2'><a href='#group_before_delete'>group_before_delete</a>
    <li class='indexItem indexItem2'><a href='#group_end_of_create'>group_end_of_create</a>
    <li class='indexItem indexItem2'><a href='#group_end_of_update'>group_end_of_update</a>
    <li class='indexItem indexItem2'><a href='#install_before_final_checks'>install_before_final_checks</a>
    <li class='indexItem indexItem2'><a href='#install_update_db'>install_update_db</a>
    <li class='indexItem indexItem2'><a href='#db_schema_abstract_schema'>db_schema_abstract_schema</a>
    <li class='indexItem indexItem2'><a href='#mailer_before_send'>mailer_before_send</a>
    <li class='indexItem indexItem2'><a href='#object_before_create'>object_before_create</a>
    <li class='indexItem indexItem2'><a href='#object_before_delete'>object_before_delete</a>
    <li class='indexItem indexItem2'><a href='#object_before_set'>object_before_set</a>
    <li class='indexItem indexItem2'><a href='#object_end_of_create'>object_end_of_create</a>
    <li class='indexItem indexItem2'><a href='#object_end_of_create_validators'>object_end_of_create_validators</a>
    <li class='indexItem indexItem2'><a href='#object_end_of_set'>object_end_of_set</a>
    <li class='indexItem indexItem2'><a href='#object_end_of_set_all'>object_end_of_set_all</a>
    <li class='indexItem indexItem2'><a href='#object_end_of_update'>object_end_of_update</a>
    <li class='indexItem indexItem2'><a href='#page_before_template'>page_before_template</a>
    <li class='indexItem indexItem2'><a href='#product_confirm_delete'>product_confirm_delete</a>
    <li class='indexItem indexItem2'><a href='#sanitycheck_check'>sanitycheck_check</a>
    <li class='indexItem indexItem2'><a href='#product_end_of_create'>product_end_of_create</a>
    <li class='indexItem indexItem2'><a href='#sanitycheck_repair'>sanitycheck_repair</a>
    <li class='indexItem indexItem2'><a href='#template_before_create'>template_before_create</a>
    <li class='indexItem indexItem2'><a href='#template_before_process'>template_before_process</a>
    <li class='indexItem indexItem2'><a href='#webservice'>webservice</a>
    <li class='indexItem indexItem2'><a href='#webservice_error_codes'>webservice_error_codes</a>
  </ul>
  <li class='indexItem indexItem1'><a href='#SEE_ALSO'>SEE ALSO</a>
</ul>
</div>

<h1><a class='u' href='#___top' title='click to go to top of document'
name="NAME"
>NAME</a></h1>

<p>Bugzilla::Hook - Extendable extension hooks for Bugzilla code</p>

<h1><a class='u' href='#___top' title='click to go to top of document'
name="SYNOPSIS"
>SYNOPSIS</a></h1>

<pre  class="code"> use Bugzilla::Hook;

 Bugzilla::Hook::process(&#34;hookname&#34;, { arg =&#62; $value, arg2 =&#62; $value2 });</pre>

<h1><a class='u' href='#___top' title='click to go to top of document'
name="DESCRIPTION"
>DESCRIPTION</a></h1>

<p>Bugzilla allows extension modules to drop in and add routines at arbitrary points in Bugzilla code. These points are referred to as hooks. When a piece of standard Bugzilla code wants to allow an extension to perform additional functions, it uses Bugzilla::Hook&#39;s <a href="#process" class="podlinkpod"
>&#34;process&#34;</a> subroutine to invoke any extension code if installed.</p>

<p>The implementation of extensions is described in <a href="../Bugzilla/Extension.html" class="podlinkpod"
>Bugzilla::Extension</a>.</p>

<p>There is sample code for every hook in the Example extension, located in <em  class="code">extensions/Example/Extension.pm</em>.</p>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="How_Hooks_Work"
>How Hooks Work</a></h2>

<p>When a hook named <code  class="code">HOOK_NAME</code> is run, Bugzilla looks through all enabled <a href="../Bugzilla/Extension.html" class="podlinkpod"
>extensions</a> for extensions that implement a subroutine named <code  class="code">HOOK_NAME</code>.</p>

<p>See <a href="../Bugzilla/Extension.html" class="podlinkpod"
>Bugzilla::Extension</a> for more details about how an extension can run code during a hook.</p>

<h1><a class='u' href='#___top' title='click to go to top of document'
name="SUBROUTINES"
>SUBROUTINES</a></h1>

<dl>
<dt><a name="process"
><code  class="code">process</code></a></dt>

<dd>
<dl>
<dt><a name="Description"
><b>Description</b></a></dt>

<dd>
<p>Invoke any code hooks with a matching name from any installed extensions.</p>

<p>See <a href="../Bugzilla/Extension.html" class="podlinkpod"
>Bugzilla::Extension</a> for more information on Bugzilla&#39;s extension mechanism.</p>

<dt><a name="Params"
><b>Params</b></a></dt>

<dd>
<dl>
<dt><a name="$name_-_The_name_of_the_hook_to_invoke."
><code  class="code">$name</code> - The name of the hook to invoke.</a></dt>

<dd>
<dt><a 
><code  class="code">$args</code> - A hashref. The named args to pass to the hook. They will be passed as arguments to the hook method in the extension.</a></dt>
</dl>

<dt><a name="Returns_(nothing)"
><b>Returns</b> (nothing)</a></dt>
</dl>
</dd>
</dl>

<h1><a class='u' href='#___top' title='click to go to top of document'
name="HOOKS"
>HOOKS</a></h1>

<p>This describes what hooks exist in Bugzilla currently. They are mostly in alphabetical order, but some related hooks are near each other instead of being alphabetical.</p>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="attachment_process_data"
>attachment_process_data</a></h2>

<p>This happens at the very beginning process of the attachment creation. You can edit the attachment content itself as well as all attributes of the attachment, before they are validated and inserted into the DB.</p>

<p>Params:</p>

<dl>
<dt><a 
><code  class="code">data</code> - A reference pointing either to the content of the file being uploaded or pointing to the filehandle associated with the file.</a></dt>

<dd>
<dt><a 
><code  class="code">attributes</code> - A hashref whose keys are the same as the input to <a href="../Bugzilla/Attachment.html#create" class="podlinkpod"
>&#34;create&#34; in Bugzilla::Attachment</a>. The data in this hashref hasn&#39;t been validated yet.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="auth_login_methods"
>auth_login_methods</a></h2>

<p>This allows you to add new login types to Bugzilla. (See <a href="../Bugzilla/Auth/Login.html" class="podlinkpod"
>Bugzilla::Auth::Login</a>.)</p>

<p>Params:</p>

<dl>
<dt><a name="modules"
><code  class="code">modules</code></a></dt>

<dd>
<p>This is a hash--a mapping from login-type &#34;names&#34; to the actual module on disk. The keys will be all the values that were passed to <a href="../Bugzilla/Auth.html#login" class="podlinkpod"
>&#34;login&#34; in Bugzilla::Auth</a> for the <code  class="code">Login</code> parameter. The values are the actual path to the module on disk. (For example, if the key is <code  class="code">DB</code>, the value is <em  class="code">Bugzilla/Auth/Login/DB.pm</em>.)</p>

<p>For your extension, the path will start with <em  class="code">Bugzilla/Extension/Foo/</em>, where &#34;Foo&#34; is the name of your Extension. (See the code in the example extension.)</p>

<p>If your login type is in the hash as a key, you should set that key to the right path to your module. That module&#39;s <code  class="code">new</code> method will be called, probably with empty parameters. If your login type is <i>not</i> in the hash, you should not set it.</p>

<p>You will be prevented from adding new keys to the hash, so make sure your key is in there before you modify it. (In other words, you can&#39;t add in login methods that weren&#39;t passed to <a href="../Bugzilla/Auth.html#login" class="podlinkpod"
>&#34;login&#34; in Bugzilla::Auth</a>.)</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="auth_verify_methods"
>auth_verify_methods</a></h2>

<p>This works just like <a href="#auth_login_methods" class="podlinkpod"
>&#34;auth_login_methods&#34;</a> except it&#39;s for login verification methods (See <a href="../Bugzilla/Auth/Verify.html" class="podlinkpod"
>Bugzilla::Auth::Verify</a>.) It also takes a <code  class="code">modules</code> parameter, just like <a href="#auth_login_methods" class="podlinkpod"
>&#34;auth_login_methods&#34;</a>.</p>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="bug_columns"
>bug_columns</a></h2>

<p>This allows you to add new fields that will show up in every <a href="../Bugzilla/Bug.html" class="podlinkpod"
>Bugzilla::Bug</a> object. Note that you will also need to use the <a href="#bug_fields" class="podlinkpod"
>&#34;bug_fields&#34;</a> hook in conjunction with this hook to make this work.</p>

<p>Params:</p>

<dl>
<dt><a name="columns_-_An_arrayref_containing_an_array_of_column_names._Push_your_column_name(s)_onto_the_array."
><code  class="code">columns</code> - An arrayref containing an array of column names. Push your column name(s) onto the array.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="bug_end_of_create"
>bug_end_of_create</a></h2>

<p>This happens at the end of <a href="../Bugzilla/Bug.html#create" class="podlinkpod"
>&#34;create&#34; in Bugzilla::Bug</a>, after all other changes are made to the database. This occurs inside a database transaction.</p>

<p>Params:</p>

<dl>
<dt><a name="bug_-_The_created_bug_object."
><code  class="code">bug</code> - The created bug object.</a></dt>

<dd>
<dt><a name="timestamp_-_The_timestamp_used_for_all_updates_in_this_transaction,_as_a_SQL_date_string."
><code  class="code">timestamp</code> - The timestamp used for all updates in this transaction, as a SQL date string.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="bug_end_of_create_validators"
>bug_end_of_create_validators</a></h2>

<p>This happens during <a href="../Bugzilla/Bug.html#create" class="podlinkpod"
>&#34;create&#34; in Bugzilla::Bug</a>, after all parameters have been validated, but before anything has been inserted into the database.</p>

<p>Params:</p>

<dl>
<dt><a name="params"
><code  class="code">params</code></a></dt>

<dd>
<p>A hashref. The validated parameters passed to <code  class="code">create</code>.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="bug_end_of_update"
>bug_end_of_update</a></h2>

<p>This happens at the end of <a href="../Bugzilla/Bug.html#update" class="podlinkpod"
>&#34;update&#34; in Bugzilla::Bug</a>, after all other changes are made to the database. This generally occurs inside a database transaction.</p>

<p>Params:</p>

<dl>
<dt><a name="bug"
><code  class="code">bug</code></a></dt>

<dd>
<p>The changed bug object, with all fields set to their updated values.</p>

<dt><a name="old_bug"
><code  class="code">old_bug</code></a></dt>

<dd>
<p>A bug object pulled from the database before the fields were set to their updated values (so it has the old values available for each field).</p>

<dt><a name="timestamp"
><code  class="code">timestamp</code></a></dt>

<dd>
<p>The timestamp used for all updates in this transaction, as a SQL date string.</p>

<dt><a name="changes"
><code  class="code">changes</code></a></dt>

<dd>
<p>The hash of changed fields. <code  class="code">$changes-&#62;{field} = [old, new]</code></p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="bug_fields"
>bug_fields</a></h2>

<p>Allows the addition of database fields from the bugs table to the standard list of allowable fields in a <a href="../Bugzilla/Bug.html" class="podlinkpod"
>Bugzilla::Bug</a> object, so that you can call the field as a method.</p>

<p>Note: You should add here the names of any fields you added in <a href="#bug_columns" class="podlinkpod"
>&#34;bug_columns&#34;</a>.</p>

<p>Params:</p>

<dl>
<dt><a name="columns_-_A_arrayref_containing_an_array_of_column_names._Push_your_column_name(s)_onto_the_array."
><code  class="code">columns</code> - A arrayref containing an array of column names. Push your column name(s) onto the array.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="bug_format_comment"
>bug_format_comment</a></h2>

<p>Allows you to do custom parsing on comments before they are displayed. You do this by returning two regular expressions: one that matches the section you want to replace, and then another that says what you want to replace that match with.</p>

<p>The matching and replacement will be run with the <code  class="code">/g</code> switch on the regex.</p>

<p>Params:</p>

<dl>
<dt><a name="regexes"
><code  class="code">regexes</code></a></dt>

<dd>
<p>An arrayref of hashrefs.</p>

<p>You should push a hashref containing two keys (<code  class="code">match</code> and <code  class="code">replace</code>) in to this array. <code  class="code">match</code> is the regular expression that matches the text you want to replace, <code  class="code">replace</code> is what you want to replace that text with. (This gets passed into a regular expression like <code  class="code">s/$match/$replace/</code>.)</p>

<p>Instead of specifying a regular expression for <code  class="code">replace</code> you can also return a coderef (a reference to a subroutine). If you want to use backreferences (using <code  class="code">$1</code>, <code  class="code">$2</code>, etc. in your <code  class="code">replace</code>), you have to use this method--it won&#39;t work if you specify <code  class="code">$1</code>, <code  class="code">$2</code> in a regular expression for <code  class="code">replace</code>. Your subroutine will get a hashref as its only argument. This hashref contains a single key, <code  class="code">matches</code>. <code  class="code">matches</code> is an arrayref that contains <code  class="code">$1</code>, <code  class="code">$2</code>, <code  class="code">$3</code>, etc. in order, up to <code  class="code">$10</code>. Your subroutine should return what you want to replace the full <code  class="code">match</code> with. (See the code example for this hook if you want to see how this actually all works in code. It&#39;s simpler than it sounds.)</p>

<p><b>You are responsible for HTML-escaping your returned data.</b> Failing to do so could open a security hole in Bugzilla.</p>

<dt><a name="text"
><code  class="code">text</code></a></dt>

<dd>
<p>A <b>reference</b> to the exact text that you are parsing.</p>

<p>Generally you should not modify this yourself. Instead you should be returning regular expressions using the <code  class="code">regexes</code> array.</p>

<p>The text has not been parsed in any way. (So, for example, it is not HTML-escaped. You get &#34;&#38;&#34;, not &#34;&#38;amp;&#34;.)</p>

<dt><a name="bug"
><code  class="code">bug</code></a></dt>

<dd>
<p>The <a href="../Bugzilla/Bug.html" class="podlinkpod"
>Bugzilla::Bug</a> object that this comment is on. Sometimes this is <code  class="code">undef</code>, meaning that we are parsing text that is not on a bug.</p>

<dt><a name="comment"
><code  class="code">comment</code></a></dt>

<dd>
<p>A <a href="../Bugzilla/Comment.html" class="podlinkpod"
>Bugzilla::Comment</a> object representing the comment you are about to parse.</p>

<p>Sometimes this is <code  class="code">undef</code>, meaning that we are parsing text that is not a bug comment (but could still be some other part of a bug, like the summary line).</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="buglist_columns"
>buglist_columns</a></h2>

<p>This happens in <a href="../Bugzilla/Search.html#COLUMNS" class="podlinkpod"
>&#34;COLUMNS&#34; in Bugzilla::Search</a>, which determines legal bug list columns for <em  class="code">buglist.cgi</em> and <em  class="code">colchange.cgi</em>. It gives you the opportunity to add additional display columns.</p>

<p>Params:</p>

<dl>
<dt><a 
><code  class="code">columns</code> - A hashref, where the keys are unique string identifiers for the column being defined and the values are hashrefs with the following fields:</a></dt>

<dd>
<dl>
<dt><a name="name_-_The_name_of_the_column_in_the_database."
><code  class="code">name</code> - The name of the column in the database.</a></dt>

<dd>
<dt><a name="title_-_The_title_of_the_column_as_displayed_to_users."
><code  class="code">title</code> - The title of the column as displayed to users.</a></dt>
</dl>

<p>The definition is structured as:</p>

<pre  class="code"> $columns-&#62;{$id} = { name =&#62; $name, title =&#62; $title };</pre>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="bugmail_recipients"
>bugmail_recipients</a></h2>

<p>This allows you to modify the list of users who are going to be receiving a particular bugmail. It also allows you to specify why they are receiving the bugmail.</p>

<p>Users&#39; bugmail preferences will be applied to any users that you add to the list. (So, for example, if you add somebody as though they were a CC on the bug, and their preferences state that they don&#39;t get email when they are a CC, they won&#39;t get email.)</p>

<p>This hook is called before watchers or globalwatchers are added to the recipient list.</p>

<p>Params:</p>

<dl>
<dt><a name="bug"
><code  class="code">bug</code></a></dt>

<dd>
<p>The <a href="../Bugzilla/Bug.html" class="podlinkpod"
>Bugzilla::Bug</a> that bugmail is being sent about.</p>

<dt><a name="recipients"
><code  class="code">recipients</code></a></dt>

<dd>
<p>This is a hashref. The keys are numeric user ids from the <code  class="code">profiles</code> table in the database, for each user who should be receiving this bugmail. The values are hashrefs. The keys in <i>these</i> hashrefs correspond to the &#34;relationship&#34; that the user has to the bug they&#39;re being emailed about, and the value should always be <code  class="code">1</code>. The &#34;relationships&#34; are described by the various <code  class="code">REL_</code> constants in <a href="../Bugzilla/Constants.html" class="podlinkpod"
>Bugzilla::Constants</a>.</p>

<p>Here&#39;s an example of adding userid <code  class="code">123</code> to the recipient list as though he were on the CC list:</p>

<pre  class="code"> $recipients-&#62;{123}-&#62;{+REL_CC} = 1</pre>

<p>(We use <code  class="code">+</code> in front of <code  class="code">REL_CC</code> so that Perl interprets it as a constant instead of as a string.)</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="colchange_columns"
>colchange_columns</a></h2>

<p>This happens in <em  class="code">colchange.cgi</em> right after the list of possible display columns have been defined and gives you the opportunity to add additional display columns to the list of selectable columns.</p>

<p>Params:</p>

<dl>
<dt><a 
><code  class="code">columns</code> - An arrayref containing an array of column IDs. Any IDs added by this hook must have been defined in the the <a href="#buglist_columns" class="podlinkpod"
>&#34;buglist_columns&#34;</a> hook.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="config_add_panels"
>config_add_panels</a></h2>

<p>If you want to add new panels to the Parameters administrative interface, this is where you do it.</p>

<p>Params:</p>

<dl>
<dt><a name="panel_modules"
><code  class="code">panel_modules</code></a></dt>

<dd>
<p>A hashref, where the keys are the &#34;name&#34; of the panel and the value is the Perl module representing that panel. For example, if the name is <code  class="code">Auth</code>, the value would be <code  class="code">Bugzilla::Config::Auth</code>.</p>

<p>For your extension, the Perl module would start with <code  class="code">Bugzilla::Extension::Foo</code>, where &#34;Foo&#34; is the name of your Extension. (See the code in the example extension.)</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="config_modify_panels"
>config_modify_panels</a></h2>

<p>This is how you modify already-existing panels in the Parameters administrative interface. For example, if you wanted to add a new Auth method (modifying Bugzilla::Config::Auth) this is how you&#39;d do it.</p>

<p>Params:</p>

<dl>
<dt><a name="panels"
><code  class="code">panels</code></a></dt>

<dd>
<p>A hashref, where the keys are lower-case panel &#34;names&#34; (like <code  class="code">auth</code>, <code  class="code">admin</code>, etc.) and the values are hashrefs. The hashref contains a single key, <code  class="code">params</code>. <code  class="code">params</code> is an arrayref--the return value from <code  class="code">get_param_list</code> for that module. You can modify <code  class="code">params</code> and your changes will be reflected in the interface.</p>

<p>Adding new keys to <code  class="code">panels</code> will have no effect. You should use <a href="#config_add_panels" class="podlinkpod"
>&#34;config_add_panels&#34;</a> if you want to add new panels.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="email_in_before_parse"
>email_in_before_parse</a></h2>

<p>This happens right after an inbound email is converted into an Email::MIME object, but before we start parsing the email to extract field data. This means the email has already been decoded for you. It gives you a chance to interact with the email itself before <a href="../email_in.html" class="podlinkpod"
>email_in</a> starts parsing its content.</p>

<dl>
<dt><a name="mail_-_An_Email::MIME_object._The_decoded_incoming_email."
><code  class="code">mail</code> - An Email::MIME object. The decoded incoming email.</a></dt>

<dd>
<dt><a name="fields_-_A_hashref._The_hash_which_will_contain_extracted_data."
><code  class="code">fields</code> - A hashref. The hash which will contain extracted data.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="email_in_after_parse"
>email_in_after_parse</a></h2>

<p>This happens after all the data has been extracted from the email, but before the reporter is validated, during <a href="../email_in.html" class="podlinkpod"
>email_in</a>. This lets you do things after the normal parsing of the email, such as sanitizing field data, changing the user account being used to file a bug, etc.</p>

<dl>
<dt><a name="fields_-_A_hashref._The_hash_containing_the_extracted_field_data."
><code  class="code">fields</code> - A hashref. The hash containing the extracted field data.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="enter_bug_entrydefaultvars"
>enter_bug_entrydefaultvars</a></h2>

<p><b>DEPRECATED</b> - Use <a href="#template_before_process" class="podlinkpod"
>&#34;template_before_process&#34;</a> instead.</p>

<p>This happens right before the template is loaded on enter_bug.cgi.</p>

<p>Params:</p>

<dl>
<dt><a name="vars_-_A_hashref._The_variables_that_will_be_passed_into_the_template."
><code  class="code">vars</code> - A hashref. The variables that will be passed into the template.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="flag_end_of_update"
>flag_end_of_update</a></h2>

<p>This happens at the end of <a href="../Bugzilla/Flag.html#update_flags" class="podlinkpod"
>&#34;update_flags&#34; in Bugzilla::Flag</a>, after all other changes are made to the database and after emails are sent. It gives you a before/after snapshot of flags so you can react to specific flag changes. This generally occurs inside a database transaction.</p>

<p>Note that the interface to this hook is <b>UNSTABLE</b> and it may change in the future.</p>

<p>Params:</p>

<dl>
<dt><a name="object_-_The_changed_bug_or_attachment_object."
><code  class="code">object</code> - The changed bug or attachment object.</a></dt>

<dd>
<dt><a name="timestamp_-_The_timestamp_used_for_all_updates_in_this_transaction,_as_a_SQL_date_string."
><code  class="code">timestamp</code> - The timestamp used for all updates in this transaction, as a SQL date string.</a></dt>

<dd>
<dt><a name="old_flags_-_The_snapshot_of_flag_summaries_from_before_the_change."
><code  class="code">old_flags</code> - The snapshot of flag summaries from before the change.</a></dt>

<dd>
<dt><a 
><code  class="code">new_flags</code> - The snapshot of flag summaries after the change. Call <code  class="code">my ($removed, $added) = diff_arrays(old_flags, new_flags)</code> to get the list of changed flags, and search for a specific condition like <code  class="code">added eq &#39;review-&#39;</code>.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="group_before_delete"
>group_before_delete</a></h2>

<p>This happens in <a href="../Bugzilla/Group.html#remove_from_db" class="podlinkpod"
>&#34;remove_from_db&#34; in Bugzilla::Group</a>, after we&#39;ve confirmed that the group can be deleted, but before any rows have actually been removed from the database. This occurs inside a database transaction.</p>

<p>Params:</p>

<dl>
<dt><a name="group_-_The_Bugzilla::Group_being_deleted."
><code  class="code">group</code> - The <a href="../Bugzilla/Group.html" class="podlinkpod"
>Bugzilla::Group</a> being deleted.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="group_end_of_create"
>group_end_of_create</a></h2>

<p>This happens at the end of <a href="../Bugzilla/Group.html#create" class="podlinkpod"
>&#34;create&#34; in Bugzilla::Group</a>, after all other changes are made to the database. This occurs inside a database transaction.</p>

<p>Params:</p>

<dl>
<dt><a name="group"
><code  class="code">group</code></a></dt>

<dd>
<p>The new <a href="../Bugzilla/Group.html" class="podlinkpod"
>Bugzilla::Group</a> object that was just created.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="group_end_of_update"
>group_end_of_update</a></h2>

<p>This happens at the end of <a href="../Bugzilla/Group.html#update" class="podlinkpod"
>&#34;update&#34; in Bugzilla::Group</a>, after all other changes are made to the database. This occurs inside a database transaction.</p>

<p>Params:</p>

<dl>
<dt><a name="group_-_The_changed_Bugzilla::Group_object,_with_all_fields_set_to_their_updated_values."
><code  class="code">group</code> - The changed <a href="../Bugzilla/Group.html" class="podlinkpod"
>Bugzilla::Group</a> object, with all fields set to their updated values.</a></dt>

<dd>
<dt><a name="changes_-_The_hash_of_changed_fields._$changes-&#62;{$field}_=_[$old,_$new]"
><code  class="code">changes</code> - The hash of changed fields. <code  class="code">$changes-&#62;{$field} = [$old, $new]</code></a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="install_before_final_checks"
>install_before_final_checks</a></h2>

<p>Allows execution of custom code before the final checks are done in checksetup.pl.</p>

<p>Params:</p>

<dl>
<dt><a name="silent"
><code  class="code">silent</code></a></dt>

<dd>
<p>A flag that indicates whether or not checksetup is running in silent mode. If this is true, messages that are <i>always</i> printed by checksetup.pl should be suppressed, but messages about any changes that are just being done this one time should be printed.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="install_update_db"
>install_update_db</a></h2>

<p>This happens at the very end of all the tables being updated during an installation or upgrade. If you need to modify your custom schema or add new columns to existing tables, do it here. No params are passed.</p>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="db_schema_abstract_schema"
>db_schema_abstract_schema</a></h2>

<p>This allows you to add tables to Bugzilla. Note that we recommend that you prefix the names of your tables with some word (preferably the name of your Extension), so that they don&#39;t conflict with any future Bugzilla tables.</p>

<p>If you wish to add new <i>columns</i> to existing Bugzilla tables, do that in <a href="#install_update_db" class="podlinkpod"
>&#34;install_update_db&#34;</a>.</p>

<p>Params:</p>

<dl>
<dt><a 
><code  class="code">schema</code> - A hashref, in the format of <a href="../Bugzilla/DB/Schema.html#ABSTRACT_SCHEMA" class="podlinkpod"
>&#34;ABSTRACT_SCHEMA&#34; in Bugzilla::DB::Schema</a>. Add new hash keys to make new table definitions. <em  class="code">checksetup.pl</em> will automatically add these tables to the database when run.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="mailer_before_send"
>mailer_before_send</a></h2>

<p>Called right before <a href="../Bugzilla/Mailer.html" class="podlinkpod"
>Bugzilla::Mailer</a> sends a message to the MTA.</p>

<p>Params:</p>

<dl>
<dt><a name="email_-_The_Email::MIME_object_that&#39;s_about_to_be_sent."
><code  class="code">email</code> - The <code  class="code">Email::MIME</code> object that&#39;s about to be sent.</a></dt>

<dd>
<dt><a name="mailer_args_-_An_arrayref_that&#39;s_passed_as_mailer_args_to_&#34;new&#34;_in_Email::Send."
><code  class="code">mailer_args</code> - An arrayref that&#39;s passed as <code  class="code">mailer_args</code> to <a href="../Email/Send.html#new" class="podlinkpod"
>&#34;new&#34; in Email::Send</a>.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_before_create"
>object_before_create</a></h2>

<p>This happens at the beginning of <a href="../Bugzilla/Object.html#create" class="podlinkpod"
>&#34;create&#34; in Bugzilla::Object</a>.</p>

<p>Params:</p>

<dl>
<dt><a name="class"
><code  class="code">class</code></a></dt>

<dd>
<p>The name of the class that <code  class="code">create</code> was called on. You can check this like <code  class="code">if ($class-&#62;isa(&#39;Some::Class&#39;))</code> in your code, to perform specific tasks before <code  class="code">create</code> for only certain classes.</p>

<dt><a name="params"
><code  class="code">params</code></a></dt>

<dd>
<p>A hashref. The set of named parameters passed to <code  class="code">create</code>.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_before_delete"
>object_before_delete</a></h2>

<p>This happens in <a href="../Bugzilla/Object.html#remove_from_db" class="podlinkpod"
>&#34;remove_from_db&#34; in Bugzilla::Object</a>, after we&#39;ve confirmed that the object can be deleted, but before any rows have actually been removed from the database. This sometimes occurs inside a database transaction.</p>

<p>Params:</p>

<dl>
<dt><a 
><code  class="code">object</code> - The <a href="../Bugzilla/Object.html" class="podlinkpod"
>Bugzilla::Object</a> being deleted. You will probably want to check its type like <code  class="code">$object-&#62;isa(&#39;Some::Class&#39;)</code> before doing anything with it.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_before_set"
>object_before_set</a></h2>

<p>Called during <a href="../Bugzilla/Object.html#set" class="podlinkpod"
>&#34;set&#34; in Bugzilla::Object</a>, before any actual work is done. You can use this to perform actions before a value is changed for specific fields on certain types of objects.</p>

<p>Params:</p>

<dl>
<dt><a name="object"
><code  class="code">object</code></a></dt>

<dd>
<p>The object that <code  class="code">set</code> was called on. You will probably want to do something like <code  class="code">if ($object-&#62;isa(&#39;Some::Class&#39;))</code> in your code to limit your changes to only certain subclasses of Bugzilla::Object.</p>

<dt><a name="field"
><code  class="code">field</code></a></dt>

<dd>
<p>The name of the field being updated in the object.</p>

<dt><a name="value"
><code  class="code">value</code></a></dt>

<dd>
<p>The value being set on the object.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_end_of_create"
>object_end_of_create</a></h2>

<p>Called at the end of <a href="../Bugzilla/Object.html#create" class="podlinkpod"
>&#34;create&#34; in Bugzilla::Object</a>, after all other changes are made to the database. This occurs inside a database transaction.</p>

<p>Params:</p>

<dl>
<dt><a name="class"
><code  class="code">class</code></a></dt>

<dd>
<p>The name of the class that <code  class="code">create</code> was called on. You can check this like <code  class="code">if ($class-&#62;isa(&#39;Some::Class&#39;))</code> in your code, to perform specific tasks for only certain classes.</p>

<dt><a name="object"
><code  class="code">object</code></a></dt>

<dd>
<p>The created object.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_end_of_create_validators"
>object_end_of_create_validators</a></h2>

<p>Called at the end of <a href="../Bugzilla/Object.html#run_create_validators" class="podlinkpod"
>&#34;run_create_validators&#34; in Bugzilla::Object</a>. You can use this to run additional validation when creating an object.</p>

<p>If a subclass has overridden <code  class="code">run_create_validators</code>, then this usually happens <i>before</i> the subclass does its custom validation.</p>

<p>Params:</p>

<dl>
<dt><a name="class"
><code  class="code">class</code></a></dt>

<dd>
<p>The name of the class that <code  class="code">create</code> was called on. You can check this like <code  class="code">if ($class-&#62;isa(&#39;Some::Class&#39;))</code> in your code, to perform specific tasks for only certain classes.</p>

<dt><a name="params"
><code  class="code">params</code></a></dt>

<dd>
<p>A hashref. The set of named parameters passed to <code  class="code">create</code>, modified and validated by the <code  class="code">VALIDATORS</code> specified for the object.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_end_of_set"
>object_end_of_set</a></h2>

<p>Called during <a href="../Bugzilla/Object.html#set" class="podlinkpod"
>&#34;set&#34; in Bugzilla::Object</a>, after all the code of the function has completed (so the value has been validated and the field has been set to the new value). You can use this to perform actions after a value is changed for specific fields on certain types of objects.</p>

<p>The new value is not specifically passed to this hook because you can get it as <code  class="code">$object-&#62;{$field}</code>.</p>

<p>Params:</p>

<dl>
<dt><a name="object"
><code  class="code">object</code></a></dt>

<dd>
<p>The object that <code  class="code">set</code> was called on. You will probably want to do something like <code  class="code">if ($object-&#62;isa(&#39;Some::Class&#39;))</code> in your code to limit your changes to only certain subclasses of Bugzilla::Object.</p>

<dt><a name="field"
><code  class="code">field</code></a></dt>

<dd>
<p>The name of the field that was updated in the object.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_end_of_set_all"
>object_end_of_set_all</a></h2>

<p>This happens at the end of <a href="../Bugzilla/Object.html#set_all" class="podlinkpod"
>&#34;set_all&#34; in Bugzilla::Object</a>. This is a good place to call custom set_ functions on objects, or to make changes to an object before <code  class="code">update()</code> is called.</p>

<p>Params:</p>

<dl>
<dt><a name="object"
><code  class="code">object</code></a></dt>

<dd>
<p>The <a href="../Bugzilla/Object.html" class="podlinkpod"
>Bugzilla::Object</a> which is being updated. You will probably want to do something like <code  class="code">if ($object-&#62;isa(&#39;Some::Class&#39;))</code> in your code to limit your changes to only certain subclasses of Bugzilla::Object.</p>

<dt><a name="params"
><code  class="code">params</code></a></dt>

<dd>
<p>A hashref. The set of named parameters passed to <code  class="code">set_all</code>.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="object_end_of_update"
>object_end_of_update</a></h2>

<p>Called during <a href="../Bugzilla/Object.html#update" class="podlinkpod"
>&#34;update&#34; in Bugzilla::Object</a>, after changes are made to the database, but while still inside a transaction.</p>

<p>Params:</p>

<dl>
<dt><a name="object"
><code  class="code">object</code></a></dt>

<dd>
<p>The object that <code  class="code">update</code> was called on. You will probably want to do something like <code  class="code">if ($object-&#62;isa(&#39;Some::Class&#39;))</code> in your code to limit your changes to only certain subclasses of Bugzilla::Object.</p>

<dt><a name="old_object"
><code  class="code">old_object</code></a></dt>

<dd>
<p>The object as it was before it was updated.</p>

<dt><a name="changes"
><code  class="code">changes</code></a></dt>

<dd>
<p>The fields that have been changed, in the same format that <a href="../Bugzilla/Object.html#update" class="podlinkpod"
>&#34;update&#34; in Bugzilla::Object</a> returns.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="page_before_template"
>page_before_template</a></h2>

<p>This is a simple way to add your own pages to Bugzilla. This hooks <code  class="code">page.cgi</code>, which loads templates from <em  class="code">template/en/default/pages</em>. For example, <code  class="code">page.cgi?id=fields.html</code> loads <em  class="code">template/en/default/pages/fields.html.tmpl</em>.</p>

<p>This hook is called right before the template is loaded, so that you can pass your own variables to your own pages.</p>

<p>You can also use this to implement complex custom pages, by doing your own output and then calling <code  class="code">exit</code> at the end of the hook, thus preventing the normal <code  class="code">page.cgi</code> behavior from occurring.</p>

<p>Params:</p>

<dl>
<dt><a name="page_id"
><code  class="code">page_id</code></a></dt>

<dd>
<p>This is the name of the page being loaded, like <code  class="code">fields.html</code>.</p>

<p>Note that if two extensions use the same name, it is uncertain which will override the others, so you should be careful with how you name your pages. Usually extensions prefix their pages with a directory named after their extension, so for an extension named &#34;Foo&#34;, page ids usually look like <code  class="code">foo/mypage.html</code>.</p>

<dt><a name="vars"
><code  class="code">vars</code></a></dt>

<dd>
<p>This is a hashref--put variables into here if you want them passed to your template.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="product_confirm_delete"
>product_confirm_delete</a></h2>

<p><b>DEPRECATED</b> - Use <a href="#template_before_process" class="podlinkpod"
>&#34;template_before_process&#34;</a> instead.</p>

<p>Called before displaying the confirmation message when deleting a product.</p>

<p>Params:</p>

<dl>
<dt><a name="vars_-_The_template_vars_hashref."
><code  class="code">vars</code> - The template vars hashref.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="sanitycheck_check"
>sanitycheck_check</a></h2>

<p>This hook allows for extra sanity checks to be added, for use by <em  class="code">sanitycheck.cgi</em>.</p>

<p>Params:</p>

<dl>
<dt><a name="status_-_a_CODEREF_that_allows_status_messages_to_be_displayed_to_the_user._(sanitycheck.cgi&#39;s_Status)"
><code  class="code">status</code> - a CODEREF that allows status messages to be displayed to the user. (<em  class="code">sanitycheck.cgi</em>&#39;s <code  class="code">Status</code>)</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="product_end_of_create"
>product_end_of_create</a></h2>

<p>Called right after a new product has been created, allowing additional changes to be made to the new product&#39;s attributes. This occurs inside of a database transaction, so if the hook throws an error, all previous changes will be rolled back, including the creation of the new product. (However, note that such rollbacks should not normally be used, as some databases that Bugzilla supports have very bad rollback performance. If you want to validate input and throw errors before the Product is created, use <a href="#object_end_of_create_validators" class="podlinkpod"
>&#34;object_end_of_create_validators&#34;</a> instead.)</p>

<p>Params:</p>

<dl>
<dt><a name="product_-_The_new_Bugzilla::Product_object_that_was_just_created."
><code  class="code">product</code> - The new <a href="../Bugzilla/Product.html" class="podlinkpod"
>Bugzilla::Product</a> object that was just created.</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="sanitycheck_repair"
>sanitycheck_repair</a></h2>

<p>This hook allows for extra sanity check repairs to be made, for use by <em  class="code">sanitycheck.cgi</em>.</p>

<p>Params:</p>

<dl>
<dt><a name="status_-_a_CODEREF_that_allows_status_messages_to_be_displayed_to_the_user._(sanitycheck.cgi&#39;s_Status)"
><code  class="code">status</code> - a CODEREF that allows status messages to be displayed to the user. (<em  class="code">sanitycheck.cgi</em>&#39;s <code  class="code">Status</code>)</a></dt>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="template_before_create"
>template_before_create</a></h2>

<p>This hook allows you to modify the configuration of <a href="../Bugzilla/Template.html" class="podlinkpod"
>Bugzilla::Template</a> objects before they are created. For example, you could add a new global template variable this way.</p>

<p>Params:</p>

<dl>
<dt><a name="config"
><code  class="code">config</code></a></dt>

<dd>
<p>A hashref--the configuration that will be passed to <a href="../Template.html#new" class="podlinkpod"
>&#34;new&#34; in Template</a>. See <a href="http://template-toolkit.org/docs/modules/Template.html#section_CONFIGURATION_SUMMARY" class="podlinkurl"
>http://template-toolkit.org/docs/modules/Template.html#section_CONFIGURATION_SUMMARY</a> for information on how this configuration variable is structured (or just look at the code for <code  class="code">create</code> in <a href="../Bugzilla/Template.html" class="podlinkpod"
>Bugzilla::Template</a>.)</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="template_before_process"
>template_before_process</a></h2>

<p>This hook is called any time Bugzilla processes a template file, including calls to <code  class="code">$template-&#62;process</code>, <code  class="code">PROCESS</code> statements in templates, and <code  class="code">INCLUDE</code> statements in templates. It is not called when templates process a <code  class="code">BLOCK</code>, only when they process a file.</p>

<p>This hook allows you to define additional variables that will be available to the template being processed, or to modify the variables that are currently in the template. It works exactly as though you inserted code to modify template variables at the top of a template.</p>

<p>You probably want to restrict this hook to operating only if a certain file is being processed (which is why you get a <code  class="code">file</code> argument below). Otherwise, modifying the <code  class="code">vars</code> argument will affect every single template in Bugzilla.</p>

<p><b>Note:</b> This hook is not called if you are already in this hook. (That is, it won&#39;t call itself recursively.) This prevents infinite recursion in situations where this hook needs to process a template (such as if this hook throws an error).</p>

<p>Params:</p>

<dl>
<dt><a name="vars"
><code  class="code">vars</code></a></dt>

<dd>
<p>This is the entire set of variables that the current template can see. Technically, this is a <a href="../Template/Stash.html" class="podlinkpod"
>Template::Stash</a> object, but you can just use it like a hashref if you want.</p>

<dt><a name="file"
><code  class="code">file</code></a></dt>

<dd>
<p>The name of the template file being processed. This is relative to the main template directory for the language (i.e. for <em  class="code">template/en/default/bug/show.html.tmpl</em>, this variable will contain <code  class="code">bug/show.html.tmpl</code>).</p>

<dt><a name="context"
><code  class="code">context</code></a></dt>

<dd>
<p>A <a href="../Template/Context.html" class="podlinkpod"
>Template::Context</a> object. Usually you will not have to use this, but if you need information about the template itself (other than just its name), you can get it from here.</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="webservice"
>webservice</a></h2>

<p>This hook allows you to add your own modules to the WebService. (See <a href="../Bugzilla/WebService.html" class="podlinkpod"
>Bugzilla::WebService</a>.)</p>

<p>Params:</p>

<dl>
<dt><a name="dispatch"
><code  class="code">dispatch</code></a></dt>

<dd>
<p>A hashref where you can specify the names of your modules and which Perl module handles the functions for that module. (This is actually sent to <a href="../SOAP/Lite.html#dispatch_with" class="podlinkpod"
>&#34;dispatch_with&#34; in SOAP::Lite</a>. You can see how that&#39;s used in <em  class="code">xmlrpc.cgi</em>.)</p>

<p>The Perl module name will most likely start with <code  class="code">Bugzilla::Extension::Foo::</code> (where &#34;Foo&#34; is the name of your extension).</p>

<p>Example:</p>

<pre  class="code">  $dispatch-&#62;{&#39;Example.Blah&#39;} = &#34;Bugzilla::Extension::Example::Webservice::Blah&#34;;</pre>

<p>And then you&#39;d have a module <em  class="code">extensions/Example/lib/Webservice/Blah.pm</em>, and could call methods from that module like <code  class="code">Example.Blah.Foo()</code> using the WebServices interface.</p>

<p>It&#39;s recommended that all the keys you put in <code  class="code">dispatch</code> start with the name of your extension, so that you don&#39;t conflict with the standard Bugzilla WebService functions (and so that you also don&#39;t conflict with other plugins).</p>
</dd>
</dl>

<h2><a class='u' href='#___top' title='click to go to top of document'
name="webservice_error_codes"
>webservice_error_codes</a></h2>

<p>If your webservice extension throws custom errors, you can set numeric codes for those errors here.</p>

<p>Extensions should use error codes above 10000, unless they are re-using an already-existing error code.</p>

<p>Params:</p>

<dl>
<dt><a name="error_map"
><code  class="code">error_map</code></a></dt>

<dd>
<p>A hash that maps the names of errors (like <code  class="code">invalid_param</code>) to numbers. See <a href="../Bugzilla/WebService/Constants.html#WS_ERROR_CODE" class="podlinkpod"
>&#34;WS_ERROR_CODE&#34; in Bugzilla::WebService::Constants</a> for an example.</p>
</dd>
</dl>

<h1><a class='u' href='#___top' title='click to go to top of document'
name="SEE_ALSO"
>SEE ALSO</a></h1>

<p><a href="../Bugzilla/Extension.html" class="podlinkpod"
>Bugzilla::Extension</a></p>
<p class="backlinkbottom"><b><a name="___bottom" href="../index.html" title="All Documents">&lt;&lt;</a></b></p>

<!-- end doc -->

</body></html>
